home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Languguage OS 2
/
Languguage OS II Version 10-94 (Knowledge Media)(1994).ISO
/
language
/
embedded
/
develop
/
ad2mac.arc
/
AD2MAC.DOC
< prev
next >
Wrap
Text File
|
1989-08-04
|
6KB
|
146 lines
AD2MAC.DOC 04 AUG. 1989
Generate symbol table macro file from 2500AD listing file
=========================================================
By Fai Lee Tung Steinberg, Motorola Development Systems, Austin, Texas
1. PURPOSE
AD2MAC extracts the symbols/values from the assembly language listing
file produced by the 2500AD assembler and creates a macro file that the
Motorola HDS-300 Hardware Development Station can use to obtain the
symbol information for Symbolic Debug support. An option converts the
output format for use with the Motorola CSIC Development System (CDS)
for Symbolic Debug support there also.
2. INSTALLATION
a. Files:
Mandatory:
1. AD2MAC.EXE ------ 2500AD to macro executable file.
2. 2500AD Cross Assembler product. The following 2500AD products
have been tested and verified as compatible with AD2MAC:
Description/Version Asm Executable
--------------------------------------- --------------
6805 Cross Assembler, Version 4.03a X6805.EXE
68C11 Macro Assembler, Version 4.03a X68C11.EXE
Other 2500AD compatible assemblers may also work with little
or no modifications to the AD2MAC program, but they have not
been tested yet. The assembler is not supplied with AD2MAC.
It must be purchased separately from...
2500AD Software Inc. (719) 395-8683
109 Brookdale Ave, Box 480
Buena Vista, CO 81211
Optional:
1. AD2MAC.DOC ------ The information file you are reading now.
2. AD*.BAT ------ Batch files to automate Symbolic Debug
support. Assembles and generates symbol
macro file. Currently supplied files are
AD05.BAT and AD11.BAT for 6805 and 68HC11,
respectively. These files show how to run
things and may be customized by the user.
b. Hardware:
An IBM PC/AT/XT, or true compatible running MS-DOS, PC-DOS at least
version 3.20.
c. Procedure:
Copy AD2MAC.EXE and the AD*.BAT files to your execution directory,
e.g. \bin or \exe. Set the MS-DOS "path" command properly so the
operating system can locate them for execution. The 2500AD assem-
bler should be installed per its documentation. The other option-
al files can also be copied or just listed, as desired.
3. COMMAND SYNTAX/DESCRIPTION
Syntax:
AD2MAC <ad25name> [/i] [/c]
Description:
AD2MAC reads the specified file, extracts the symbol table infor-
mation (symbol and value), and creates a symbol file with the exten-
sion .MAC. The symbol file is composed of lines of the format
"<cmd> <symbol> <value>".
For HDS-300 support, <cmd> = " @LS", and the symbol file must be
downloaded to an HDS-300 and executed with the "macro file" (MF)
command. This loads the symbols/values into the local symbol table
so HDS-300 Symbolic Debug can be accomplished.
For CDS support, <cmd>= "DEFINE", and the symbol file must be load-
ed using the "command file" (CF) command. This loads the symbols/
values into the local symbol table so CDS Symbolic Debug can be
accomplished.
Where:
<ad25name> is the name of an 2500AD assembler listing file. A
default extension of .LST is assumed.
/i is an option to ignore non-referenced, i.e. unused,
symbols. When this option is invoked, only referenced
symbols will be processed into the output macro file.
/c is an option to set AD2MAC for CDS support.
Examples:
AD2MAC myprog Processes 2500AD listing file MYPROG.LST and
creates MYPROG.MAC symbolic file in HDS-300
output format. All symbols are processed.
AD2MAC file2.lst /i Processes 2500AD listing file FILE2.LST and
creates FILE2.MAC symbolic file in HDS-300
output format. Non-referenced (unused)
symbols are ignored (not processed).
AD2MAC john /c Processes 2500AD listing file JOHN.LST and
creates JOHN.MAC symbolic file in CDS output
format. All symbols are processed.
4. RESTRICTIONS
a. Because the symbol file will be used on a CDS or HDS-300 system, it
must follow the symbol rules for that system. Thus AD2MAC operates
under the following rules:
1. All symbol names are truncated to the appropriate size for the
intended system (CDS= 31 characters, HDS-300= 8 characters).
It is up to the user to ensure symbol names are unique within
this truncated size. Symbols are case sensitive on the CDS
system ("start" not= "START"), but insensitive on the HDS-300
("start" = "START").
2. The following characters are valid for symbol names: letters,
numbers, period (.), underscore (_), and dollar sign ($)
3. Symbol names must begin with a letter, period, or underscore.
4. Invalid symbol name characters found in the input file will be
replaced by underscore characters.
5. Symbol names like ".25" should be avoided because of possible
parsing confusion (is ".25" a symbol name or a real number?).
b. Multiple modules, i.e. relocatable (relative) assemblies, are not
supported in this version. This version was intended to only
support single module, absolute assemblies.
5. BUG FIXED
a. None.
6. KNOWN BUGS
a. None.
*** EOF ***